Skip to content

Update sentry-rails 5.22.0 → 5.22.4 (patch)#1415

Closed
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/group/sentry-ruby-core-5.22.4
Closed

Update sentry-rails 5.22.0 → 5.22.4 (patch)#1415
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/group/sentry-ruby-core-5.22.4

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Feb 7, 2025

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ sentry-rails (5.22.0 → 5.22.4) · Repo · Changelog

Release Notes

5.22.4

Bug Fixes

  • Fix handling of cron with tz in Cron::Job (#2530)
  • Revert "[rails] support string errors in error reporter (#2464)" (#2533)
  • Removed unnecessary warning about missing stackprof when Vernier is configured as the profiler (#2537)
  • Fix regression with CheckInEvent in before_send (#2541)

Internal

  • Introduced Configuration#validate to validate configuration in Sentry.init block (#2538)
  • Introduced Sentry.dependency_installed? to check if a 3rd party dependency is available ie Sentry.dependency_installed?(:Vernier) (#2542)

5.22.3

Bug Fixes

  • Accept Hash in before_send* callbacks again (#2529)

5.22.2

Features

  • Improve the accuracy of duration calculations in cron jobs monitoring (#2471)
  • Use attempt_threshold to skip reporting on first N attempts (#2503)
  • Support code.namespace for Ruby 3.4+ stacktraces (#2506)

Bug fixes

  • Default to internal_error error type for OpenTelemetry spans #2473
  • Improve before_send and before_send_transaction's return value handling (#2504)
  • Fix a crash when calling Sentry.get_main_hub in a trap context (#2510)
  • Use URI::RFC2396_PARSER.escape explicitly to remove warning logs to stderr (#2509)

Internal

  • Test Ruby 3.4 in CI (#2506)
  • Upgrade actions workflows versions (#2506)
  • Stop relying on fugit (#2519)

5.22.1

Bug Fixes

  • Safe-navigate to session flusher #2396
  • Fix latency related nil error for Sidekiq Queues Module span data #2486

Does any of this look wrong? Please let us know.

✳️ sentry-ruby (5.22.0 → 5.22.4) · Repo · Changelog

Release Notes

5.22.4

Bug Fixes

  • Fix handling of cron with tz in Cron::Job (#2530)
  • Revert "[rails] support string errors in error reporter (#2464)" (#2533)
  • Removed unnecessary warning about missing stackprof when Vernier is configured as the profiler (#2537)
  • Fix regression with CheckInEvent in before_send (#2541)

Internal

  • Introduced Configuration#validate to validate configuration in Sentry.init block (#2538)
  • Introduced Sentry.dependency_installed? to check if a 3rd party dependency is available ie Sentry.dependency_installed?(:Vernier) (#2542)

5.22.3

Bug Fixes

  • Accept Hash in before_send* callbacks again (#2529)

5.22.2

Features

  • Improve the accuracy of duration calculations in cron jobs monitoring (#2471)
  • Use attempt_threshold to skip reporting on first N attempts (#2503)
  • Support code.namespace for Ruby 3.4+ stacktraces (#2506)

Bug fixes

  • Default to internal_error error type for OpenTelemetry spans #2473
  • Improve before_send and before_send_transaction's return value handling (#2504)
  • Fix a crash when calling Sentry.get_main_hub in a trap context (#2510)
  • Use URI::RFC2396_PARSER.escape explicitly to remove warning logs to stderr (#2509)

Internal

  • Test Ruby 3.4 in CI (#2506)
  • Upgrade actions workflows versions (#2506)
  • Stop relying on fugit (#2519)

5.22.1

Bug Fixes

  • Safe-navigate to session flusher #2396
  • Fix latency related nil error for Sidekiq Queues Module span data #2486

Does any of this look wrong? Please let us know.

↗️ bigdecimal (indirect, 3.1.8 → 3.1.9) · Repo · Changelog

Release Notes

3.1.9 (from changelog)

  • Accept no digits in the fractional part (#302)

    @kou

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 15 commits:

↗️ logger (indirect, 1.6.2 → 1.6.6) · Repo

Sorry, we couldn't find anything useful about this release.


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Feb 7, 2025
@mitlib mitlib temporarily deployed to thesis-submit-pr-1415 February 7, 2025 13:22 Inactive
@depfu depfu bot force-pushed the depfu/update/group/sentry-ruby-core-5.22.4 branch from 0220764 to 907a5a8 Compare February 21, 2025 14:30
@coveralls
Copy link

coveralls commented Feb 21, 2025

Coverage Status

coverage: 98.313%. remained the same
when pulling ecec82c on depfu/update/group/sentry-ruby-core-5.22.4
into 6407965 on main.

@depfu depfu bot force-pushed the depfu/update/group/sentry-ruby-core-5.22.4 branch from 907a5a8 to ecec82c Compare February 25, 2025 13:26
@depfu
Copy link
Contributor Author

depfu bot commented Mar 3, 2025

Closing because this update has already been applied

@depfu depfu bot closed this Mar 3, 2025
@depfu depfu bot deleted the depfu/update/group/sentry-ruby-core-5.22.4 branch March 3, 2025 13:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants